Repository navigation
Conversation
Fixes the 0404 failure at reset_blob on HP EliteBook x360 1040 G6. Tested only on that laptop.
|
blobs_00cb.py is the only blob which my 06cb:00b7 0x969 chip accepts with status 0000 after Also, blobs.py is where your code change should go. This is where the table for all the different hardware vs correct blob is specified. |
|
@Karloss1234 Thanks for testing. That matches what I saw on my 00b7. I'll move the change into blobs.py where the hardware-to-blob table lives and push an update to this branch. |
Same blobs as blobs_9a except reset_blob, which this chip accepts (9a's is rejected with 0404). Done in blobs.py so factory_reset in sensor.py gets it too, and the init_flash.py special case is reverted. Suggested by Karloss1234 in the PR.
|
Pushed an update moving the change into blobs.py as you suggested @Karloss1234 , thanks. |
|
Merged — thanks @Primal-Origin and @Karloss1234. While reviewing I checked the blob sets: |
Device: HP EliteBook x360 1040 G6, USB 06cb:00b7 (sensor type 0x969), CachyOS, Python 3.14.
Problem: after clearing the sensor with the BIOS fingerprint reset, init_flash fails at the reset_blob step with status 0404. factory_reset in sensor.py hits the same rejection. Related upstream thread: uunicorn#225.
Change: in blobs.py, 06cb:00b7 now loads blobs_00cb instead of blobs_9a. blobs_00cb matches blobs_9a except for reset_blob (checked for the other three blobs), and its reset_blob is accepted by this chip while 9a's is rejected with 0404. Doing it in blobs.py covers init_flash.py and factory_reset. An earlier version of this PR special-cased init_flash.py; that is reverted.
Testing: with this change the service stays up, fprintd-enroll completes and fprintd-verify works. Another 06cb:00b7 owner (Karloss1234) reports the same blob as the only one their chip accepts.